Data driven configuration of call management applications

ABSTRACT

A call manager uses a call management application in conjunction with a live dial database to control routing of calls for managed devices. To generate the live dial database, the call management application accesses configured route patterns and enters these patterns into the live dial database. Upon identifying an expansion indicator in a configured route pattern, the call management application accesses dial plan data that includes multiple route pattern definitions that each define a pattern using one or more sub-strings and, for each sub-string, an associated tag. The call management application then enters patterns defined by the route pattern definitions into the live dial database based on various other criteria established for the configured route pattern having the expansion indicator.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.12/330,135 filed Dec. 8, 2008 and entitled “Data Driven Configuration ofCall Management Applications” which is a continuation of U.S.application Ser. No. 09/867,918 filed May 29, 2001 and entitled “DataDriven Configuration of Call Management Applications” now U.S. Pat. No.7,463,729.

TECHNICAL FIELD OF THE INVENTION

The present invention relates generally to call management and, moreparticularly, to data driven configuration of call managementapplications.

BACKGROUND OF THE INVENTION

With the growing complexity of telecommunications systems, managementand configuration of call control equipment has become increasingly morecomplicated. For example, with the expansion of Internet protocol (IP)voice communications, call control equipment must often controltelephony communications over and between multiple differentcommunication networks. Moreover, because telecommunication protocolsare driven by regional requirements, such as the North AmericanNumbering Plan (NANP), call control equipment and applications are oftenlimited in their portability.

SUMMARY OF THE INVENTION

In accordance with the present invention, techniques for data drivenconfiguration of call management applications are provided whichsubstantially eliminate or reduce disadvantages and problems associatedwith previous techniques. In a particular embodiment, the presentinvention satisfies a need for a call management application thatinitializes and provides call management by accessing a separate,configurable set of dial plan data.

According to one embodiment of the present invention, a method fortelephony call management maintains dial plan data defining multipleroute patterns. These route pattern definitions each include one or moresub-strings, with each sub-string having an associated tag. The methodalso maintains configured routing data that includes at least oneconfigured route pattern that has an expansion indicator. The methodaccesses the configured routing data to read the configured routepattern, identifies the expansion indicator in the configured routepattern, and accesses the dial plan data responsive to identifying theexpansion indicator. For each of the route pattern definitions in thedial plan data, the method generates a route pattern based on the routepattern definition and enters the generated route pattern into a livedial database for use in routing calls placed by users.

Embodiments of the present invention provide numerous technicaladvantages. Using a telephony call management application having aseparate, configurable dial plan allows an administrator to install anduse the application in any suitable geographic region, simply byobtaining and/or generating an appropriate set of dial plan data.Moreover, separation of the dial plan data from the call managementapplication permits modifications to the dial plan data in case ofchanging regional requirements and permits customization of dial plansbased upon specific customer requirements. In addition, particularembodiments maintain the dial plan data as a relatively easy to modifyfile, such as an ASCII text file.

Other technical advantages of the present invention will be readilyapparent to one skilled in the art from the following figures,descriptions and claims. Moreover, while specific advantages have beenenumerated above, various embodiments may include all, some or none ofthe enumerated advantages.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present invention and itsadvantages, reference is now made to the following description, taken inconjunction with the accompanying drawings, in which:

FIG. 1 illustrates exemplary components of a call manager having a callmanagement application and configurable dial plan data for use by thecall management application;

FIG. 2 illustrates an interface for configuring a route pattern havingan expansion indicator for triggering the call management application toaccess a configurable dial plan data file;

FIGS. 3 a, 3 b, 3 c and 3 d are tables illustrating selected dial plandata for use by a call management application during initialization; and

FIG. 4 is a flowchart illustrating a method for initializing a callmanagement application based upon configurable dial plan data thatincludes a number of route pattern definitions.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 illustrates a call manager 12 that includes a processor 14, anetwork interface 16, and a memory 18. Within memory 18, call manager 12maintains a call manager application 20, network configuration data 22,and configured routing data 24, which includes one or more routepatterns 26. Within memory 18, call manager 12 also maintains dial plandata 28 and a live dial database 30. In general, call manager 12, usingcall manager application 20, manages telephony communications for one ormore managed devices. This includes the routing of calls from thesedevices using information maintained in live dial database 30. Togenerate live dial database 30, call manager application 20 accessesroute patterns 26 to identify routing configurations specified by anadministrator. Call manager application 20 may detect an expansionindicator in one or more of these configured route patterns 26 and, inresponse, expands on the patterns to include information from dial plandata 28 in live dial database 30. Thus expansion indicators serve as“wildcards” in a route pattern that, when detected, indicate for callmanager application 20 to expand using information from dial plan data28.

Call manager 12 represents any suitable collection and arrangement ofcomponents at one or more locations that operate to manage and controltelephony communications for devices within one or more tenants. Thus,processor 14 represents one or more microprocessors, controllers, logicdevices and/or other suitable equipment for executing software, logic orother control applications such as call manager application 20. Networkinterface 16 represents hardware and any associated controlling logicfor linking components of call manager 12 and for coupling call manager12 to other devices and communication networks. For example, networkinterface 16 may couple to an Internet Protocol (IP) network that linksmanaged IP telephony devices of a tenant.

Memory 18 represents any suitable collection and arrangement of volatileor non-volatile, local or remote data storage devices. In the embodimentillustrated, memory 18 stores call manager application 20, networkconfiguration data 22, configured routing data 24, dial plan data 28,and live dial database 30. Call manager application 20 represents logic,such as computer software, for controlling the operation of call manager12, including the management of telephony communications for manageddevices. Network configuration data 22 represents information describingcoupled networks, network configurations, managed devices, and otherappropriate network information for controlling the routing andmanagement of telephony communications. For example, networkconfiguration data 22 may include an IP address of call manager 12 andinformation identifying various available gateways for routingpacket-based telephone calls placed from managed devices to equipmentcoupled to the public switched telephone network (PSTN).

Configured routing data 24 includes route patterns 26 that have been setby an administrator and/or other device to specify the routing oftelephone calls from managed devices. For example, a selected routepattern 26 may specify a pattern to match against dialed digits receivedfrom a managed device and an indication of a device or devices to routethe call to upon matching the dialed digits to the specified pattern.For example, a selected route pattern 26 may specify a pattern thatmatches telephone numbers having an area code in Dallas and a gateway inDallas for routing matching telephone calls into the PSTN. Thus, for acall matching the pattern, call manager 12 may route the call across anIP network to the specified gateway, with the gateway then transitioningthe call into the PSTN. In addition, because call manager 12 may routetelephone calls among various devices having different protocols and/ordifferent network addressing plans, route patterns 26 may also specifytransformations to the digits identifying the calling party as well asthe digits identifying the called party. For example, to map numbersfrom the PSTN to a private network, call manager 12 may transform aten-digit number into a four-digit number expected by the privatenetwork.

Dial plan data 28 specifies information for transforming, processing,and/or expanding on route patterns 26 as call manager application 20generates live dial database 30. In the example illustrated, dial plandata 28 includes pattern processing data 32 and a numbering plan 34 thatspecifies a number of route pattern definitions 36. Pattern processingdata 32 includes information for combination with route patterns 26 bycall manager application 20 in order to generate entries for live dialdatabase 30. For example, pattern processing data 32 may specifyavailable numbering plans 34, tags available for these numbering plans,and dialing transformations keyed off of these available tags. Thus,pattern processing data 32 specifies options for processing selectedroute patterns 26 when generating entries in live dial database 30.

For example, pattern processing data 32 may specify“INTERNATIONAL-ACCESS” as one of the available tags and a route filterthat prevents any pattern from entering live dial database 30 if thepattern has a sub-string with a tag matching INTERNATIONAL-ACCESS. Inaddition, these tags may be used to transform numbers matching topatterns. For example, “AREA-CODE” may be specified as a tag, andpattern processing data 32 may define a dialing transformation thatalters dialed digits matching a selected route pattern 26 by keeping ordiscarding the area code of the dialed number.

Dial plan data 28 also includes one or more numbering plans 34 thatdefine the route patterns for particular regions or define customizednumbering plans. In the example illustrated, numbering plan 34 containsroute pattern definitions 36 to define route patterns for the NorthAmerican Numbering Plan (NANP). Each route pattern definition 36 definesa string for a route pattern using one or more sub-strings andassociated tags for some or all of the sub-strings. These associatedtags match to and/or define the tags available in pattern processingdata 32 for processing route patterns 26. According to a particularembodiment, call manager 12 implements numbering plan 34 as a text filehaving a series of entries such as the following:

# P: Digit pattern -- PATTERN TAG # T: Type of Number -- I(nternational)or N(ational) # W: Network Specific Facilities -- OP or OP/P or OPXXX orOPXXXX # U: Urgent pattern? (Call extended immediately on match) # 0 P:0 LOCAL-OPERATOR T: N W: OP # 00 P: 00 LONG-DISTANCE-OPERATOR T: N W:OP/P # [2-9]11 P: [2-9]11 SERVICE T: N U: Y # 0+[2-9][02-9]XXXXX P: 0LOCAL-OPERATOR P: [2-9][02-9]X OFFICE-CODE P: XXXX SUBSCRIBER T: N W: OP# 0+[2-9]X[02-9]XXXX P: 0 LOCAL-OPERATOR P: [2-9]X[02-9] OFFICE-CODE P:XXXX SUBSCRIBER T: N W: OP # 0+[2-9][02-9]X[2-9]XXXXXX P: 0LONG-DISTANCE-OPERATOR P: [2-9][02-9]X AREA-CODE P: [2-9]XX OFFICE-CODEP: XXXX SUBSCRIBER T: N W: OP # 0+[2-9]X[02-9][2-9]XXXXXX P: 0LONG-DISTANCE-OPERATOR P: [2-9]X[02-9] AREA-CODE P: [2-9]XX OFFICE-CODEP: XXXX SUBSCRIBER T: N W: OP # 1+[2-9][02-9]X[2-9]XXXXXX P: 1LONG-DISTANCE-DIRECT-DIAL P: [2-9][02-9]X AREA-CODE P: [2-9]XXOFFICE-CODE P: XXXX SUBSCRIBER T: N

The preceding route pattern definitions illustrate a particular methodfor defining patterns for numbering plans 34. As illustrated by thisselected portion of the North American Numbering Plan, each patterndefinition defines a particular pattern for potentially comparing withdigits dialed by a device managed by call manager 12. Thus, to fullyimplement a selected numbering plan, a file and/or other data structuremay potentially have tens or hundreds of route pattern definitions 36.

In the embodiment illustrated in the preceding text, the route patterndefinition each use one or more text lines to identify sub-strings of arouting pattern as well as a tag associated with that sub-string. Forexample, the first route pattern definition in the preceding textprovides routing for a device dialing the digit zero to reach anoperator. The first line of this definition, which begins with the poundsign (#), serves as a comment describing the string to match and doesnot affect the actual route pattern definition. Each subsequent linebeginning with a “P” defines a sub-string and a tag associated with thesub-string. However, to reach an operator, only a single sub-string formatching to the digit zero and having the associated tag for“LOCAL-OPERATOR” is defined. Within each of the pattern definitions,tags identify the defined sub-strings of a pattern. Because thesedefinitions associate various portions of defined patterns with tags,call manager 12 and administrators may relatively easily handle andmanipulate these defined routing patterns.

Moreover, as shown by the preceding text, numbering plan 34 can maintainsome or all of the available and/or defined routing patterns for aparticular region in a relatively easy to access and modify format.However, while the preceding text illustrates a particular embodimentfor defining a selected numbering plan 34 as a series of text routepattern definitions, call manager 12 contemplates using any suitableconfigurable data format for providing route pattern definitions 36 fornumbering plans 34.

Numbering plan 34 provides an easy to use and configure data source fordefining available routing patterns for call manager 12. To enter someor all of the routing patterns defined by numbering plan 34 into livedial database 30, an administrator need only specify a single routepattern 26 that includes an expansion indicator. Then, atinitialization, call manager application 20 identifies the expansionindicator in route pattern 26 and, in response, accesses numbering plan34 to potentially add routing patterns into live dial database 30 foreach route pattern definition 36. Thus, using route patterns 26 and dialplan data 28 when appropriate, call manager application 20 populateslive dial database 30 with routing patterns for routing telephone callsfrom managed devices.

While the embodiment illustrated includes specific data sets maintainedas various separate blocks, call manager 12 contemplates any suitableseparation and/or combination of various routing data, so long as callmanager 12 provides a configurable set of definitions for routingpatterns, with this set of definitions available for entry into livedial database 30 based upon a single configured route pattern. Thus,call manager 12 may maintain pattern processing data 32 and numberingplans 34 in any suitable format, such as tables in a database and/or oneor more text files.

FIG. 2 illustrates an interface for receiving information for generatinga selected route pattern 26 in configured routing data 24. In theexample illustrated, interface 40 includes a route pattern field 42, apartition field 44, a numbering plan field 46, a route filter field 48,and a gateway/route list field 50. Interface 40 also includes fields forspecifying dialing transformations such as calling party transformations52 and called party transformations 54. Using route pattern field 42, anadministrator may specify a pattern for entry into live dial database 30and, using gateway/route list field 50, may specify a particular deviceor devices to which to potentially route dialed digits matching thepattern entered in route pattern field 42. Moreover, by including anexpansion indicator within route pattern field 42, an administrator mayindicate an intent to include all route patterns defined for thenumbering plan identified in numbering plan field 46.

In the example illustrated, the pattern in route pattern field 42 is“9.@” with the @ serving as an expansion indicator. Moreover, numberingplan field 46 indicates for call manager application 20 to access theNorth American Numbering Plan to expand the pattern. Thus, the specifiedpattern in route pattern plan 42 will potentially result in the additionof routing patterns into live dial database 30 for dialed numbersbeginning with a number 9 and followed by any set of valid digits for aNorth American telephone number. Thus, any valid North American number,when proceeded by the digit 9, may be routed to the gateway and/or otherdevices specified by gateway/route list field 50.

To limit the various patterns from the North American Numbering Planentered into live dial database 30 by call manager application 20,interface 40 provides route filter field 48. Using route filter field48, an administrator may indicate selected patterns or types of patternsto exclude from live dial database 30, despite these patterns beingdefined in numbering plan 34 for the North American Numbering Plan.According to a particular embodiment, the route filters available forselection and/or specified by an administrator in route filter field 48identify patterns from the North American Numbering Plan to discardand/or keep using the tags associated with the patterns. For example, aselected route filter may permit the entry of only patterns not havingan “INTERNATIONAL-ACCESS” tag defined for the pattern. Thus, while theNorth American Numbering Plan may include valid patterns for callinginternational numbers that include the INTERNATIONAL-ACCESS Tag, callmanager application 20 will filter out these patterns when generatinglive dial database 30. Since calls only precede upon matching a patternin live dial database 30, the route filter described prevents users fromplacing international calls unless permitted by another one ofconfigured route patterns 26. Therefore, the association of tags withsub-strings within patterns allows for a relatively simple manipulationof patterns to be added or excluded from live dial database 30.

Interface 40 also permits an administrator to specify dialingtransformations to the dialed digits and/or the digits identifying thecalling party. As with the route filters, these dialing transformationsmay specify manipulations of called and/or calling party digits basedupon tags defined in route pattern definitions 36. For example, using adigit discard field 56, an administrator may specify specificsub-strings of called party digits to keep and/or discard using tagsdefined by route pattern definitions 36. Thus, a particular digitdiscard instruction may specify, for example, the particular sub-stringsfrom a dialed number to maintain when converting any eleven-digit orten-digit number to a seven-digit number. For this conversion, the digitdiscard instruction may specify to keep the sub-strings identified bythe tags “OFFICE-CODE” and “SUBSCRIBER.” When applied, this digitdiscard instruction results in call manager application 20 transformingany dialed digits matching the specified pattern into a seven-digitnumber. However, while this example illustrates a specific operationdefined for discarding digits, call manager 12 contemplates providingany appropriate dialing transformations for operation upon called and/orcalling party digits based upon tags defined in route patterndefinitions 36.

Moreover, while interface 40 illustrates a particular embodiment for anadministrator to configure route patterns 26, call manager 12contemplates presenting any suitable interface having fields appropriatefor specifying a routing pattern, with the option of specifying arouting pattern for expansion into some or all of the valid routingpatterns for a particular numbering plan.

FIGS. 3 a, 3 b, 3 c and 3 d illustrate selected portions of patternprocessing data 32 maintained as four tables. These include a numberingplan table 60, a tag table 64, a digit discard instructions (DDI) table68, and a DDI member table 72.

Numbering plan table 60 identifies various numbering plans 34 available,which in this example, includes the North American Numbering Plan(NANP). However, numbering plan table 60 may include a listing of one ormore available numbering plans and may include customized numberingplans, such as a customization of the North American Numbering Plan.According to a particular embodiment, call manager application 20accesses numbering plan table 60 to provide options for administratorsconfiguring routing data. For example, during configuration of aselected route pattern 26, interface 40, using numbering plan field 46,may present the various numbering plans 34 listed in numbering plantable 60.

Tag table 64 provides a listing of tags associated with various portionsof telephone numbers. For example, for the telephone number (214)555-1234, the tag “AREA-CODE” identifies 214, the tag “OFFICE-CODE”identifies 555, and the tag “SUBSCRIBER” identifies 1234. Thus, usingthese tags, call manager 12 may identify, modify, and operate on dialeddigits and route patterns. The tags listed in tag table 64 may bepermanently configured, configurable by an administrator, and/orautomatically generated based on tags in numbering plans 34. Forexample, call manager application 20 or other suitable applications mayaccess numbering plans 34 to determine all available tags and populatetag table 64 with these tags.

DDI table 68 identifies predefined dialing transformations forapplication to dialed digits. In this example, predefined digit discardinstructions for numbering plan number 1 (NANP) provide ten-digit toseven-digit transformation, discarding of digits preceding a “period” ina route pattern, and for discarding digits that attempt to select aparticular long-distance carrier. According to a particular embodiment,interface 40 presents the digit discard instructions in digit discardinstructions field 56 based upon the instructions listed for numberingplan 34 selected in numbering plan field 46. For example, if anadministrator selects the NANP, call manager application 20 may identifyall available digit discard instructions for this numbering plan andpresent those instructions as options in DDI field 56. This provides anadministrator with pre-configured options for selecting dialingtransformations with these digit discard instructions.

DDI member table 72 details operations for discarding or maintainingportions of dialed digits based on tags for the digit discardinstructions listed in DDI table 68. In the example illustrated, DDImember table 72 provides instructions for achieving the three firstinstructions listed in DDI table 68. For the first digit discardinstruction, DDI member table 72 provides instructions for obtaining aseven digit number having the appropriate digits from a dialed number.Thus, DDI member table 72 indicates to maintain tags nine and ten(OFFICE-CODE and SUBSCRIBER). Similarly, for the third digit discardinstruction, 1010 (equal access suppression), DDI member table 72indicates to discard tags five and six (TRANSIT-NETWORK-ESCAPE andTRANSIT-NETWORK), which prevents a caller from selecting an alternatelong distance carrier.

While the preceding tables illustrate specific information maintainedusing a particular format, call manager 12 contemplates maintainingpattern processing data 32 using any appropriate data storage techniquesand arrangements. Thus, while these examples illustrate a particularembodiment for providing pattern processing data 32 that specifiesmanipulations of digits based upon tags associated with sub-strings ofmatching route patterns, call manager 12 may maintain and/or access thisinformation in any suitable format, and this pattern processing data 32may be incorporated within other data, such as within individualnumbering plans 34 and route pattern definitions 36.

FIG. 4 is a flowchart illustrating a method for call manager 12, uponexecuting call manager application 20, to populate live dial database 30based upon configured routing data 24 and dial plan data 28. Callmanager 12 accesses network configuration data 22 to determine anappropriate configuration, such as an Internet Protocol (IP) address forcall manager 12, and other suitable information at step 100. Callmanager 12 accesses configured routing data 24 at step 102 and selectsan unprocessed route pattern 26 at step 104. Call manager 12 determineswhether the pattern includes an expansion indicator, such as the @ sign,at step 106, and if not, adds the patterns to live dial database 30 withany associated transformations at step 108. For example, for a routepattern configured using interface 40 that does not include an expansionindicator, call manager 12 enters the route pattern into live dialdatabase 30 along with an indication that numbers matching that routepattern are to be routed to the gateway and/or route list specified ingateway/route list field 50. Moreover, live dial database 30 may alsoreflect any dialing transformations specified in interface 40 for thisroute pattern.

If route pattern 26 includes an expansion indicator, call manager 12accesses route pattern definitions 36 at step 110 and selects anunprocessed route pattern definition 36 at step 112. Based upon routefilters determined at step 114, call manager 12 determines whether theseroute filters exclude the pattern defined by route pattern definition 36at step 116. For example, the selected route pattern definition 36 maydefine a route pattern having an INTERNATIONAL-ACCESS tag and the routefilters specified may exclude any route patterns having this tag. Ifexcluded by the route filters, call manager 12 does not include thepattern defined by route pattern definition 36 in live dial database 30.However, if not excluded by the route filters, call manager 12constructs a route pattern from the route pattern definition at step 118and adds the constructed route pattern with associated dialingtransformations to live dial database 30 at step 120. Call manager 12determines whether unprocessed route pattern definitions 36 remain atstep 122. If so, call manager 12 proceeds through route patterndefinitions 36 in numbering plan 34 and adds each of these route patterndefinitions 36 into live dial database 30 unless excluded by routefilters.

Thus, by including an expansion indicator in a configured route pattern26, an administrator may include some or all of the route patternsdefined for numbering plan 34 based upon selected route filters. Afterprocessing all route pattern definitions 36 in numbering plan 34, callmanager 12 determines whether unprocessed configured route patterns 26remain at step 124. If so, call manager 12 again determines whether theselected route pattern 26 includes an expansion indicator and addsappropriate entries into live dial database 30 based upon route pattern26. After processing route patterns 26, this stage of initialization oflive dial database 30 is complete.

While this flowchart illustrates an exemplary method of operation, callmanager 12 may use any suitable techniques for accessing configuredrouting patterns and when necessary, expanding these routing patternsusing a set of route pattern definitions defining patterns assub-strings with associated tags. Thus, many of the steps in thisflowchart may take place simultaneously and/or in different orders thanas shown. In addition, call manager 12 may use methods with additionalsteps, fewer steps and/or different steps, so long as the methods remainappropriate. Thus, the example provided by this flowchart is merelyillustrative, and call manager 12 contemplates using any suitable stepsfor initializing a live dial database 30 based upon configurable dialplan data.

Although the present invention has been described in severalembodiments, a myriad of changes and modifications may be suggested toone skilled in the art, and it is intended that the present inventionencompass such changes and modifications as fall within the scope of thepresent appended claims.

1. A telephony call management apparatus comprising: a memory storing: acall management application; a live dial database; configured routingdata comprising at least one configured route pattern that includes anexpansion indicator; and dial plan data comprising a plurality of routepattern definitions; and a processor operable, when executing the callmanagement application: to access each route pattern in the configuredrouting data; to identify the expansion indicator; and responsive toidentifying the expansion indicator: to access the dial plan data; andfor each of the route pattern definitions in the dial plan data: togenerate a route pattern based on the route pattern definition; and toenter the generated route pattern into the live dial database.
 2. Theapparatus of claim 1, wherein: the dial plan data implements the NorthAmerican Numbering Plan; and the live dial database specifies routing oftelephone calls from managed voice over Internet protocol (VoIP)devices.
 3. The apparatus of claim 1, wherein: the configured routingdata further comprise a route filter; and the processor is furtheroperable, for each of the route pattern definitions in the dial plandata, to generate the route pattern and to enter the generated routepattern into the live dial database based on the route filter.
 4. Theapparatus of claim 3, wherein the route filter specifies valid routepatterns using tags associated with each route pattern.
 5. The apparatusof claim 1, wherein the configured routing data further comprise digitdiscard instructions, the digit discard instructions specifying digitsto retain when routing calls placed by users, the digits specified usingtags associated with the configured route pattern.
 6. The apparatus ofclaim 1, wherein the configured routing data further comprise digittransformation instructions, the digit transformation instructionsspecifying a modification to perform on matched digits, the matcheddigits and the modification to perform specified tags associated withthe configured route pattern.
 7. A method for telephony call managementcomprising: maintaining dial plan data comprising a plurality of routepattern definitions; maintaining configured routing data comprising aconfigured route pattern including an expansion indicator; accessing theconfigured routing data to read the configured route pattern;identifying the expansion indicator in the configured route pattern;accessing the dial plan data responsive to identifying the expansionindicator; and while accessing the dial plan data, for each of the routepattern definitions in the dial plan data: generating a route patternbased on the one or more sub-strings for the route pattern definition;and entering the generated route pattern into a live dial database foruse in routing calls placed by users.
 8. The method of claim 7, wherein:the dial plan data implements the North American Numbering Plan; and thelive dial database specifies routing of telephone calls from managedvoice over Internet protocol (VoIP) devices.
 9. The method of claim 7,wherein: the configured routing data further comprise a route filter;and the method further comprises, for each of the route patterndefinitions in the dial plan data, generating the route pattern andentering the generated route pattern into the live dial database basedon the route filter.
 10. The method of claim 9, wherein the route filterspecifies valid route patterns tags associated with each route pattern.11. The method of claim 7, wherein the configured routing data furthercomprise digit discard instructions, the digit discard instructionsspecifying digits to retain when routing calls placed by users, thedigits specified using tags associated with the configured routepattern.
 12. The method of claim 7, wherein the configured routing datafurther comprise digit transformation instructions, the digittransformation instructions specifying a modification to perform onmatched digits, the matched digits and the modification to performspecified tags associated with the configured route pattern.
 13. Logicfor telephony call management, the logic encoded in media and operablewhen executed to: maintain dial plan data comprising a plurality ofroute pattern definitions; maintain configured routing data comprising aconfigured route pattern including an expansion indicator; access theconfigured routing data to read the configured route pattern; identifythe expansion indicator in the configured route pattern; access the dialplan data responsive to identifying the expansion indicator; and whileaccessing the dial plan data, for each of the route pattern definitionsin the dial plan data: generate a route pattern based on the routepattern definition; and enter the generated route pattern into a livedial database for use in routing calls placed by users.
 14. The logic ofclaim 13, wherein: the dial plan data implements the North AmericanNumbering Plan; and the live dial database specifies routing oftelephone calls from managed voice over Internet protocol (VoIP)devices.
 15. The logic of claim 13, wherein: the configured routing datafurther comprise a route filter; and the logic is further operable, foreach of the route pattern definitions in the dial plan data, to generatethe route pattern and to enter the generated route pattern into the livedial database based on the route filter.
 16. The logic of claim 15,wherein the route filter specifies valid route patterns using tagsassociated with each route pattern.
 17. The logic of claim 13, whereinthe configured routing data further comprise digit discard instructions,the digit discard instruction specifying digits to retain when routingcalls placed by users, the digits specified using tags associated witheach route pattern.
 18. The logic of claim 13, wherein the configuredrouting data further comprise digit transformation instructions, thedigit transformation instructions specifying a modification to performon matched digits, the matched digits and the modification to performspecified tags associated with the configured route pattern.
 19. Atelephony call management apparatus comprising: means for maintainingdial plan data comprising a plurality of route pattern definitions;means for maintaining configured routing data comprising a configuredroute pattern including an expansion indicator; means for accessing theconfigured routing data to read the configured route pattern; means foridentifying the expansion indicator in the configured route pattern; andmeans for accessing the dial plan data responsive to identifying theexpansion indicator and, for each of the route pattern definitions inthe dial plan data: generating a route pattern based on the routepattern definition; and entering the generated route pattern into a livedial database for use in routing calls placed by users.
 20. Thetelephony call management apparatus of claim 19, wherein the configuredrouting data further comprise a route filter, the telephony callmanagement apparatus further comprising means, for each of the routepattern definitions in the dial plan data, for generating the routepattern and entering the generated route pattern into the live dialdatabase based on the route filter.
 21. The telephony call managementapparatus of claim 19, wherein the configured routing data furthercomprise digit discard instructions, the digit discard instructionsspecifying digits to retain when routing calls placed by users, thedigits specified using the tags associated with the configured routepattern.